home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: munta.cs.mu.OZ.AU!fjh
- From: fjh@munta.cs.mu.OZ.AU (Fergus Henderson)
- Subject: Re: Exception and what to put into them
- Message-ID: <9600501.20425@mulga.cs.mu.OZ.AU>
- Sender: news@cs.mu.OZ.AU (CS-Usenet)
- Organization: Computer Science, University of Melbourne, Australia
- References: <49i7hh$aco@news1.mclink.it> <4an868$def@newsbf02.news.aol.com> <4cg7kr$9iq@dub-news-svc-6.compuserve.com>
- Date: Thu, 4 Jan 1996 14:35:49 GMT
-
- 100754.2730@compuserve.com (Martin Aupperle) writes:
-
- >dstkelley@aol.com (Dstkelley) wrote:
- >
- >>It is my humble opinion that logging the line number of where the
- >>exception occured is short sided thinking. [...]
- [...]
- >Using class names/function names instead is much more effort since the
- >necessary strings cannot be generated automatically.
-
- Sure they can - at least if your compiler supports it.
- In GNU C++ you can use __FUNCTION__ or __PRETTY_FUNCTION__
- in the same way that you can use __LINE__.
-
- There is some chance that something like this may be standardized in C9X.
-
- --
- Fergus Henderson WWW: http://www.cs.mu.oz.au/~fjh
- fjh@cs.mu.oz.au PGP: finger fjh@128.250.37.3
-